Limit display of objects for a certain user/group

Hi! I have a question about limiting the access rights to certain objects in a module.
Basically, I do not want to display all objects in a module for a specific user/group. Is it possible to limit the access rights to a specific view?
sarli - Tue Dec 15 04:47:41 EST 2009

Re: Limit display of objects for a certain user/group
ePiallat - Tue Dec 15 04:47:41 EST 2009

Hi,

Yes you can, but not this way.

You can limit the access rights to a specific view, but it won't prevent anyone to remove filter or add columns to current display, so it won't protect any data except the view definitions themselves.

You can however set specific access rights to any object or attribute. You can't however set specific access for a specific attribute of a specific object. (either the whole object or a specific attribute for every object in module).

Re: Limit display of objects for a certain user/group
Lion29 - Sat Jan 16 06:58:34 EST 2010

ePiallat - Tue Dec 15 04:47:41 EST 2009
Hi,

Yes you can, but not this way.

You can limit the access rights to a specific view, but it won't prevent anyone to remove filter or add columns to current display, so it won't protect any data except the view definitions themselves.

You can however set specific access rights to any object or attribute. You can't however set specific access for a specific attribute of a specific object. (either the whole object or a specific attribute for every object in module).

Hi,
i do agree that we can restrict the visibility of some objects by making use of the "Read-Lock Data".
But in one of my project, they have implemented a way in which the object is entirely hidden from the user/group. even it does not show as "Read-Lock Data" against that particular object. When we search for the hidden object, it pops up the message box "Object Not Found"..

Do you have any idea of how to do this...

Re: Limit display of objects for a certain user/group
Mathias Mamsch - Sat Jan 16 17:41:39 EST 2010

Lion29 - Sat Jan 16 06:58:34 EST 2010
Hi,
i do agree that we can restrict the visibility of some objects by making use of the "Read-Lock Data".
But in one of my project, they have implemented a way in which the object is entirely hidden from the user/group. even it does not show as "Read-Lock Data" against that particular object. When we search for the hidden object, it pops up the message box "Object Not Found"..

Do you have any idea of how to do this...

I never heard or read of anything like that. The part of the module editor, where the objects are shown is built in the doors.exe, I can think only of some really ugly ways to change its standard behaviour.

The only ways I know of to make objects "disappear" is:
a) filter them out (check if a filter is active)
b) delete them (check if they appear in the show deletions list)
c) corrupt your database or the memory (e.g. delete a section file or modify the doors internal data structures)

Maybe the project people have made the objects invisible by denying the file access to the section file in the database (if this is even possible without errors), or they really overused the filter functions or something else. Or they placed a very bad hack to unlink the object in the hierarchy by modifying the internal data structures of DOORS. However this works, I am 99% sure this is not possible using simple DXL.

Regards, Mathias

Re: Limit display of objects for a certain user/group
Lion29 - Wed Feb 03 14:20:36 EST 2010

Mathias Mamsch - Sat Jan 16 17:41:39 EST 2010
I never heard or read of anything like that. The part of the module editor, where the objects are shown is built in the doors.exe, I can think only of some really ugly ways to change its standard behaviour.

The only ways I know of to make objects "disappear" is:
a) filter them out (check if a filter is active)
b) delete them (check if they appear in the show deletions list)
c) corrupt your database or the memory (e.g. delete a section file or modify the doors internal data structures)

Maybe the project people have made the objects invisible by denying the file access to the section file in the database (if this is even possible without errors), or they really overused the filter functions or something else. Or they placed a very bad hack to unlink the object in the hierarchy by modifying the internal data structures of DOORS. However this works, I am 99% sure this is not possible using simple DXL.

Regards, Mathias

Hi Mathias,
I've checked in the filter also, everything is as ususal. There seems to be no change. It appears as usual. I'm sure that they have provided the access rights for a group of persons. They should have made use of this trick only i guess...

But the mystery is how is it possible that it gets hidden for other group of users????

Re: Limit display of objects for a certain user/group
Mathias Mamsch - Fri Feb 05 06:08:42 EST 2010

Lion29 - Wed Feb 03 14:20:36 EST 2010
Hi Mathias,
I've checked in the filter also, everything is as ususal. There seems to be no change. It appears as usual. I'm sure that they have provided the access rights for a group of persons. They should have made use of this trick only i guess...

But the mystery is how is it possible that it gets hidden for other group of users????

I guess this will remain a mystery :-) In my opinion there are two possibilities: A bad (or good) hack of doors.exe/the process memory of doors.exe or otherwise it is an undocumented unkown feature of DOORS. What version are you using?

Regards, Mathias

Re: Limit display of objects for a certain user/group
Lion29 - Mon Feb 08 03:33:19 EST 2010

Mathias Mamsch - Fri Feb 05 06:08:42 EST 2010
I guess this will remain a mystery :-) In my opinion there are two possibilities: A bad (or good) hack of doors.exe/the process memory of doors.exe or otherwise it is an undocumented unkown feature of DOORS. What version are you using?

Regards, Mathias

we make use of 8.3 version